Skip to main content
POST
Add messages [OSS + Cloud]

Authorizations

Authorization
string
header
required

API key issued by EverOS, sent as Authorization: Bearer <api_key>.

Body

application/json
session_id
string
required

The conversation these messages belong to (1–128 characters). It is the unit extraction works on: /api/v2/memory/flush takes this id, and a session boundary is what triggers extraction on its own.

Required string length: 1 - 128
messages
MessageItem · object[]
required

The turns to append, in order — 1 to 500 per call. Each carries its own sender and timestamp, so one call can hold a whole exchange.

Required array length: 1 - 500 elements
app_id
string
default:default

Business-semantic scope for this write, defaulting to "default". Reads must use the same app_id / project_id pair to see what was written under it. Note this is a partition, not the security boundary — that is the tenant resolved from your API key.

project_id
string
default:default

Second half of the business-semantic scope, defaulting to "default". See app_id.

async_mode
boolean
default:true

Selects the write path. true (default): validated and enqueued asynchronously → HTTP 202 with status "queued". false: forwarded synchronously to the engine, returning its 200 result and surfacing write errors directly. Extraction is always asynchronous (flush-triggered).

Response

Synchronous write result (async_mode=false).

request_id
string
required

Request trace id (peer to data)

data
AddData · object
required

Endpoint-defined business result